Closes: #9837

Description

This PR increases the app's resilience when Product fields have unexpected types:

• When a product's SKU is a number instead of a String.
• When a product's weight is a number instead of a String.
• When a product dimensions (length, width, height) are a number instead of a String.
• When a product download's ID is a number instead of a String.

It uses failsafe decoding to handle those alternative types, and adds to the unit test for parsing alternative types in a Product. (These are known decoding errors that users have experienced.)

Testing instructions

We don't know the exact plugins that can cause this behavior, but you can test using a tool like Charles Proxy or Proxyman to intercept and modify the response:

1. Set a breakpoint in your tool of choice for requests to the /wc/v3/products endpoint.
2. Build and run the app.
3. Open the Products tab.
4. Modify the response in one or more of the following ways:
   • A product's SKU is a number (e.g. "sku": 123 or see the product-alternative-types.json mock for an example).
   • A product's weight is a number (e.g. "weight": 213).
   • A product's dimensions is a number (e.g. "dimensions": { "length": 12, "width": 33, "height": 54 }).
   • A product's download ID is a number (e.g. "downloads": [{ "id" : 12345, "name" : "Song #1", "file" : "https://example.com/woo-single-1.ogg" }]).
5. Execute the response and confirm the app loads the product list.

Screenshots

Before	After

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.